Demoting partial tracks from a first cache to a second cache

ABSTRACT

A determination is made of a track to demote from the first cache to the second cache, wherein the track in the first cache corresponds to a track in the storage system and is comprised of a plurality of sectors. In response to determining that the second cache includes a the stale version of the track being demoted from the first cache, a determination is made as to whether the stale version of the track includes track sectors not included in the track being demoted from the first cache. The sectors from the track demoted from the first cache are combined with sectors from the stale version of the track not included in the track being demoted from the first cache into a new version of the track. The new version of the track is written to the second cache.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No. 13/352,239, filed Jan. 17, 2012, which is incorporated herein by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a computer program product, system, and method for demoting partial tracks from a first cache to a second cache.

2. Description of the Related Art

A cache management system buffers tracks in a storage device recently accessed as a result of read and write operations in a faster access storage device, such as memory, than the storage device storing the requested tracks. Subsequent read requests to tracks in the faster access cache memory are returned at a faster rate than returning the requested tracks from the slower access storage, thus reducing read latency. The cache management system may also return complete to a write request when the modified track directed to the storage device is written to the cache memory and before the modified track is written out to the storage device, such as a hard disk drive. The write latency to the storage device is typically significantly longer than the latency to write to a cache memory. Thus, using cache also reduces write latency.

A cache management system may maintain a linked list having one entry for each track stored in the cache, which may comprise write data buffered in cache before writing to the storage device or read data. In the commonly used Least Recently Used (LRU) cache technique, if a track in the cache is accessed, i.e., a cache “hit”, then the entry in the LRU list for the accessed track is moved to a Most Recently Used (MRU) end of the list. If the requested track is not in the cache, i.e., a cache miss, then the track in the cache whose entry is at the LRU end of the list may be removed (or destaged back to storage) and an entry for the track data staged into cache from the storage is added to the MRU end of the LRU list. With this LRU cache technique, tracks that are more frequently accessed are likely to remain in cache, while data less frequently accessed will more likely be removed from the LRU end of the list to make room in cache for newly accessed tracks.

There is a need in the art for improved techniques for using cache in a storage system.

SUMMARY

Provided are a computer program product, system, and method for demoting partial tracks from a first cache to a second cache. A determination is made of a track to demote from the first cache to the second cache, wherein the track in the first cache corresponds to a track in the storage system and is comprised of a plurality of sectors. A determination is made of whether the second cache includes a stale version of the track being demoted from the first cache. In response to determining that the second cache includes the stale version of the track, a determination is made as to whether the stale version of the track includes track sectors not included in the track being demoted from the first cache. The sectors from the track demoted from the first cache are combined with sectors from the stale version of the track not included in the track being demoted from the first cache into a new version of the track. The new version of the track is written to the second cache.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a computing environment.

FIG. 2 illustrates an embodiment of first cache management information.

FIG. 3 illustrates an embodiment of second cache management information.

FIG. 4 illustrates an embodiment of a first cache control block.

FIG. 5 illustrates an embodiment of a second cache control block.

FIG. 6 illustrates an embodiment of stride information.

FIG. 7 illustrates an embodiment of a second cache RAID configuration.

FIG. 8 illustrates an embodiment of a storage RAID configuration.

FIG. 9 illustrates an embodiment of operations to demote unmodified non-sequential tracks from the first cache to promote to the second cache.

FIG. 10 illustrates an embodiment of operations to add a track to the first cache.

FIG. 11 illustrates an embodiment of operations to process a track to demote form the first cache to the second cache.

FIG. 12 illustrates an embodiment of operations to add tracks from the first stride to the second stride.

FIG. 13 illustrates an embodiment of operations to free space in the second cache.

FIG. 14 illustrates an embodiment of operations to process a request for tracks to return to a read request.

DETAILED DESCRIPTION

Described embodiments provide techniques for demoting tracks from a first cache to a second cache. If the track to demote comprises a partial track and if the second track includes a stale version of the track, then a new version of the track may be created in the second cache including the sectors from the partial track being demoted from the first cache combined with sectors in the stale version of the track in the second cache that are not included in the sectors of the partial track being demoted. The new version of the track may be written to a new location of the second cache.

FIG. 1 illustrates an embodiment of a computing environment. A plurality of hosts 2 a, 2 b . . . 2 n may submit Input/Output (I/O) requests to a storage controller 4 over a network 6 to access data at volumes 8 (e.g., Logical Unit Numbers, Logical Devices, Logical Subsystems, etc.) in a storage 10. The storage controller 4 includes a processor complex 12, including one or more processors with single or multiple cores, a first cache 14 and a second cache 18. The first 14 and second 18 caches cache data transferred between the hosts 2 a, 2 b . . . 2 n and the storage 10.

The storage controller 4 has a memory 20 that includes a storage manager 22 for managing the transfer of tracks transferred between the hosts 2 a, 2 b . . . 2 n and the storage 10 and a cache manager 24 that manages data transferred between the hosts 2 a, 2 b . . . 2 n and the storage 10 in the first cache 14, and the second cache 18. A track may comprise any unit of data configured in the storage 10, such as a track, Logical Block Address (LBA), etc., which is part of a larger grouping of tracks, such as a volume, logical device, etc. The cache manager 24 maintains first cache management information 26 and second cache management information 28 to manage read (unmodified) and write (modified) tracks in the first cache 14 and the second cache 18.

The storage manager 22 and cache manager 24 are shown in FIG. 1 as program code loaded into the memory 20 and executed by the processor complex 12. Alternatively, some or all of the functions may be implemented in hardware devices in the storage controller 4, such as in Application Specific Integrated Circuits (ASICs).

The second cache 18 may store tracks in a log structured array (LSA) 32, where tracks are written in a sequential order as received, thus providing a temporal ordering of the tracks written to the second cache 18. In an LSA, later versions of tracks already present in the LSA are written at the end of the LSA 32. In alternative embodiments, the second cache 18 may store data in formats other than in an LSA.

The memory 20 further includes second cache RAID configuration information 34 providing information on a RAID configuration used to determine how to form a stride of tracks to store in the second cache 18. In one embodiment, the second cache 18 may be comprised of a plurality of storage devices, such as separate solid state storage devices (SSDs), such that the strides formed of tracks from the first cache 14 are striped across the separate storage devices forming the second cache 18, such as flash memories. In a further embodiment, the second cache 18 may comprise a single storage device, such as one flash memory, such that the tracks are grouped in strides as defined by the second cache RAID configuration 34, but the tracks are written as strides to a single device, such as one flash memory, implementing the second cache 18. The tracks of strides configured for the second cache RAID configuration 34 may be written to the LSA 32 in the second cache 18 device. The second cache RAID configuration 34 may specify different RAID levels, e.g., levels 5, 10, etc.

The memory 20 further includes storage RAID configuration information 36 providing information on a RAID configuration used to determine how to write tracks from the first cache 14 or second cache 18, if the second cache 18 should store modified data, to the storage system 10, where the tracks in the destaged stride are striped across the storage devices, such as disk drives in the storage system 10.

In one embodiment, the first cache 14 may comprise a Random Access Memory (RAM), such as a Dynamic Random Access Memory (DRAM), and the second cache 18 may comprise a flash memory, such as a solid state device, and the storage 10 is comprised of one or more sequential access storage devices, such as hard disk drives and magnetic tape. The storage 10 may comprise a single sequential access storage device or may comprise an array of storage devices, such as a Just a Bunch of Disks (JBOD), Direct Access Storage Device (DASD), Redundant Array of Independent Disks (RAID) array, virtualization device, etc. In one embodiment, the first cache 14 is a faster access device than the second cache 18, and the second cache 18 is a faster access device than the storage 10. Further, the first cache 14 may have a greater cost per unit of storage than the second cache 18 and the second cache 18 may have a greater cost per unit of storage than storage devices in the storage 10.

The first cache 14 may be part of the memory 20 or implemented in a separate memory device, such as a DRAM.

In certain embodiments, the second cache may comprise a read only cache caching tracks demoted from the first cache 14.

The network 6 may comprise a Storage Area Network (SAN), a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, an Intranet, etc.

FIG. 2 illustrates an embodiment of the first cache management information 26 including a track index 50 providing an index of tracks in the first cache 14 to control blocks in a control block directory 52; an unmodified sequential LRU list 54 providing a temporal ordering of unmodified sequential tracks in the first cache 14; a modified LRU list 56 providing a temporal ordering of modified sequential and non-sequential tracks in the first cache 14; an unmodified non-sequential LRU list 58 providing a temporal ordering of unmodified non-sequential tracks in the first cache 14; and stride information 60 providing information on strides formed of unmodified non-sequential tracks in the first cache 14 to write to the second cache 18 as a full stride write.

In certain embodiments, upon determining that the first cache 18 is full, the modified LRU list 56 is used to destage modified tracks from the first cache 14 to the storage 10 so that the copy of those destaged tracks in the first cache 18 may be discarded to make room in the first cache 18 for new modified tracks.

Once a modified non-sequential track is destaged from the first cache 14 to the storage 10, then the cache manager 24 may designate that destaged tracks as an unmodified non-sequential track in the first cache 14 and add indication of the newly designated unmodified track to the unmodified non-sequential LRU list 58, from where it is eligible to be promoted to the second cache 14. The state of the destaged modified track may be changed by updating the first cache control block 104 to indicate the destaged modified non-sequential track as unmodified in field 106. Thus, unmodified non-sequential tracks in the first cache 14 may comprise read data or modified non-sequential tracks that were destaged to the storage 10 according to the modified LRU list 56. Thus, destaged modified tracks that become unmodified tracks in the LRU list 58 may be promoted to the second cache 14 to be available for subsequent read requests. In these embodiments, the second cache 14 comprises a read only cache to cache unmodified non-sequential tracks.

FIG. 3 illustrates an embodiment of the second cache management information 28 including a track index 70 providing an index of tracks in the second cache 18 to control blocks in a control block directory 72; an unmodified list 74 providing a temporal ordering of unmodified tracks in the second cache 18; and stride information 78 providing information on strides of tracks written to the second cache 18. In one embodiment, the second cache 18 only stores unmodified, non-sequential tracks. In further embodiments, the second cache 18 may also store modified and/or sequential tracks.

All the LRU lists 54, 56, 58, and 74 may include the track IDs of tracks in the first cache 14 and the second cache 18 ordered according to when the identified track was last accessed. The LRU lists 54, 56, 58, and 74 have a most recently used (MRU) end indicating a most recently accessed track and a LRU end indicating a least recently used or accessed track. The track IDs of tracks added to the caches 14 and 18 are added to the MRU end of the LRU list and tracks demoted from the caches 14 and 18 are accessed from the LRU end. The track indexes 50 and 70 may comprise a scatter index table (SIT). Alternative type data structures may be used to provide the temporal ordering of tracks in the caches 14 and 18.

Non-sequential tracks may comprise Online Line Transaction Processing (OLTP) tracks, which often comprise small block writes that are not fully random and have some locality of reference, i.e., have a probability of being repeatedly accessed.

FIG. 4 illustrates an embodiment of a first cache control block 100 entry in the control block directory 52, including a control block identifier (ID) 102, a first cache location 104 of the physical location of the track in the first cache 14, information 106 indicating whether the track is modified or unmodified, information 108 indicating whether the track is a sequential or non-sequential access, information 110 indicating a demote status for the track, such as no demotion, ready to demote, and demote complete, and a sector map 112 indicating sectors of the track included in the first cache 14. If the sector map 112 indicates that certain of the sectors of the track in the first cache 14 do not have data, then the track maintained in the first cache 14 comprises a partial track.

FIG. 5 illustrates an embodiment of a second cache control block 120 entry in the second cache control block directory 72, including a control block identifier (ID) 122; an LSA location 124 where the track is located in the LSA 32; modified/unmodified info 126 indicating whether the track is modified or unmodified; valid/invalid flag 128 indicating whether the track is valid or invalid; and a sector map 129 indicating sectors of the track included in the second cache 18. A track in the second cache 18 is indicated as invalid if the track is updated in the first cache 14 or if the track is demoted from the second cache 18. If the sector map 129 indicates that certain of the sectors of the track in the second cache 18 do not have data, then the track maintained in the second cache 18 comprises a partial track. The cache control block 120 may not include the field 126 if the second cache 18 only stores unmodified read data.

FIG. 6 illustrates an instance 130 of the stride information 60, 78 for one stride to be formed in the second cache 18, including a stride identifier (ID) 132, tracks 134 of the storage 10 included in the stride 132, and an occupancy 136 indicating a number of valid tracks in the stride of the total number of tracks, where the tracks in the stride that are not valid are eligible for garbage collection operations.

FIG. 7 illustrates an embodiment of the second cache RAID configuration 34 that is maintained to determine how to form strides of tracks in the second cache 18 from the tracks in the first cache 14. A RAID level 140 indicates the RAID configuration to use, e.g., RAID 1, RAID 5, RAID 6, RAID 10, etc., a number of data disks (m) 142 storing tracks of user data, and a number of parity disks (p) 144 storing parity calculated from the data disks 142, where p can be one or more, indicating the number of disks for storing the calculated parity blocks. An unmodified parity optional flag 148 indicates whether parity should be calculated for unmodified non-sequential tracks in the first cache 14 being promoted to the second cache 18. This optional flag 148 allows for only including unmodified non-sequential tracks in a stride to fill the stride with only unmodified non-sequential tracks. The stride of unmodified non-sequential tracks in the first cache 14 may be indicated in an LSA 32, where the tracks of the stride are striped across m plus p storage devices forming the second cache 18. Alternatively, the second cache 18 may comprise fewer than n devices.

FIG. 8 illustrates an embodiment of the storage RAID configuration 36 that is maintained to determine how to form strides of modified tracks in the second cache 18 to stripe across the disks of the storage 10. A RAID level 150 indicates the RAID configuration to use, a number of data disks (m) 152 storing tracks of user data, and a number of parity disks (p) 154 storing parity calculated from the data disks 152, where p can be one or more, indicating the number of disks for storing the calculated parity blocks. The stride of tracks from the second cache 18 may be striped across disks in the storage system 10.

In one embodiment, the second cache 34 and storage 36 RAID configurations may provide different parameters or have the same parameters, such as different RAID levels, data disks, parity disks, etc.

FIG. 9 illustrates an embodiment of operations performed by the cache manager 24 to demote unmodified non-sequential tracks from the first cache 14 to promote to the second cache 18, where the unmodified non-sequential tracks may be selected from the LRU end of the unmodified non-sequential LRU list 58 when space is needed. Upon initiating (at block 200) the operation to demote selected unmodified non-sequential tracks, the demote status 110 (FIG. 4) of the unmodified non-sequential tracks selected to demote is set (at block 202) to “ready”. The cache manager 24 uses (at block 204) the second cache RAID configuration information 34 to form a first stride of tracks from the first cache 114 to promote to a stride in the second cache 18. For instance, forming the first stride of tracks may comprise forming a stride for a RAID configuration based on a RAID configuration defined 34 for the second cache as having n devices including m devices for storing tracks of data and at least one parity device p to store parity data calculated from the tracks of data for the m devices. Further, the first stride of tracks may be striped across n solid state storage devices without parity to form the second stride in embodiments where the second cache comprises at least n solid state storage devices.

The cache manager 24 processes (at block 206) the unmodified non-sequential LRU 58 list to determine a number of unmodified non-sequential tracks having a demote status 110 of ready in their control blocks 100. If the cache manager 24 determines (at block 208) that the number of unmodified non-sequential tracks is sufficient to form a stride, then the cache manager 24 populates (at block 210) the first stride of unmodified non-sequential tracks having a demote status 110 of ready. In one embodiment, the first stride may be populated starting from the LRU end of the unmodified non-sequential LRU list 58 and use enough tracks for the data disks in stride. If (at block 212) the RAID configuration specifies parity disks, then the cache manager 24 calculates (at block 212) parity for the unmodified non-sequential tracks included in the stride and includes parity data (for the p parity disks) in the stride. If (at block 208) there are not sufficient unmodified non-sequential tracks in the first cache 14 to fill the first stride, then control ends until there are a sufficient number of unmodified non-sequential tracks having the demote ready status available to populate the first stride.

After populating the first stride (at blocks 210 and 212), the cache manager 14 determines (at block 214) a free second stride in the second cache 18 in which to include the tracks from the first stride. The tracks from the first stride are written or striped (at block 216) as a full stride write to the second stride across the devices forming the second cache 18. Upon filling the second stride in the second cache 18 with the tracks from the first stride, the cache manager 14 indicates (at block 218) the occupancy 136 of the stride information 130 for the second stride as full. The cache manager 24 updates (at block 220) the demote status 110 for the unmodified non-sequential tracks included in the stride as demote “complete”.

Although the operations of FIG. 9 are described as demoting unmodified non-sequential tracks from the first cache 14 to promote to the second cache 18, in alternative embodiments, the operations may apply to demoting different types of tracks, such as modified, sequential, etc.

With the described embodiments, the unmodified tracks from the first cache 14 are gathered and written as a stride to the second cache 18 so that one Input/Output (I/O) operation is used to transfer multiple tracks.

In certain embodiments, the tracks maintained in the first cache 14 may comprise partial tracks, which comprise tracks having data for only a subset of the sectors of the track. This may occur because the cache manager 24 may only stage in from the storage 10 sectors of a track that are requested by a read request, not all the sectors of the track. In case that the first cache 14 stores partial tracks as well as full tracks (tracks having data for all sectors of the track) for certain tracks, more partial tracks may be included in a stride than full tracks and more partial tracks having more empty sectors may be included in a stride than partial tracks having fewer empty sectors, i.e., fuller partial tracks. Thus, a stride can be packed with more partial tracks from the first cache 14 having fewer sectors than tracks having more sectors. Further, the second cache 18 may store partial tracks demoted from the first cache 14. Thus, the tracks included in the first stride from the first cache 14 that are written to the second stride in the second cache 18 may comprise full tracks and/or partial tracks.

FIG. 10 illustrates an embodiment of operations performed by the cache manager 24 to add, i.e., promote, a track to the first cache 14, which track may comprise a write or modified track from a host 2 a, 2 b . . . 2 n, a non-sequential track in the second cache 18 that is subject to a read request and as a result moved to the first cache 14, or read requested data not found in either cache 14 or 18 and retrieved from the storage 10. Upon receiving (at block 240) the track to add to the first cache 14, if (at block 242) a copy of the track is already included in the first cache 14, then the cache manager 24 writes (at block 244) the received track to first cache 14. The cache control block 100 (FIG. 4) for the track is updated (at block 246) to indicate the location 104 having the updated track, the data type (modified/unmodified 106 and sequential/non-sequential 108), the demote status 110, and the sector map 112 is updated to indicate the sectors in the updated track having data. The entry for the updated track in the appropriate LRU list 54, 56, 58 is moved (at block 248) to the MRU end of the list 54, 56, 58.

If (at block 242) the track to add to the first cache 14 is not already in the first cache 14, then the cache manager 24 creates (at block 250) a control block 100 (FIG. 4) for the track to add indicating the location 104 in the first cache 14 and whether the track is modified/unmodified 106 and sequential/non-sequential 108, and indicate in the sector map 112 the sectors for the track having data. This control block 100 is added to the control block directory 52 of the first cache 14. The cache manager 24 adds (at block 252) an entry to the first cache track index 50 having the track ID of the track to add and an index to the created cache control block 100 in the control block directory 52. An entry is added (at block 254) to the MRU end of the LRU list 54, 56 or 58 of the track type of the track to add. If (at block 256) the track to add is a modified non-sequential track and if (at block 258) a copy of the track to add is in the second cache 18, as determined from the second cache track index 70, then the copy of the track in the second cache 18 is invalidated (at block 260), such as by setting the valid/invalid flag 128 in the second cache control block 120 for the track in the second cache 18 to invalid. If (at block 256) the track to add is unmodified sequential, control ends.

FIG. 11 illustrates an embodiment of operations performed by the cache manager 24 to demote a track from the first cache 14 to the second cache 18. Upon processing (at block 280) a track to demote from the first cache 14, if (at block 282) the second cache 18 track index 70 indicates that the second cache 18 does not include a stale (older) version of the track than the version being demoted from the first cache 14, then the cache manager 24 writes (at block 284) the track being demoted, which may comprise a partial or full track, to a new version of the track at a new location in the second cache 18. The cache manager 24 creates (at block 286) a second cache control block 120 (FIG. 5) for the written track indicating the LSA location 124, that the track has valid data 128, and the sectors of the written track that are non-empty in the sector map 129. The cache manager 24 adds (at block 288) an entry to the MRU end of the LRU list 74 for the track added to the second cache 18.

If (at block 282) the second cache 18 includes a stale version of the track, then the cache manager 24 determines (at block 290) whether the track being demoted includes data for all the sectors of the track (i.e., is a full track, not a partial track). The determination of whether the track being demoted is partial or full may be determined from the sector map 112 in the first cache control block 100 (FIG. 4) for the track being demoted. If (at block 290) the track is a full track, then the cache manager 24 writes (at block 292) the full track being demoted to a new version of the track at a new location in the second cache 18.

If (at block 290) the track being demoted is a partial track, i.e., the sector map 112 for the track indicates empty sectors, then the cache manager 24 determines (at block 294) from the sector map 129 for the second cache 18 whether the stale version in the second cache 18 of the partial track being demoted includes track sectors not included in the partial track being demoted from the first cache 14. The stale version of the track may comprise a partial track or a full track. The determination of the sectors of the stale version of the track having data may be determined from the sector map 129 in the second cache control block 120 (FIG. 5) for the stale version of the track already in the second cache 18. If the stale version includes sectors not included in the partial track being demoted, then the cache manager 24 combines (at block 296) the sectors from the partial track demoted from the first cache 14 with sectors from the stale version of the track not included in the partial track being demoted into a new version of the track to store at a new location in the second cache 18. The cache manager 24 writes (at block 298) the new version of the track to a new location in the second cache 18. If (at block 294) the stale version of the track being demoted does not include track sectors not included in the partial track being demoted, then the cache manager 24 writes (at block 300) the partial track being demoted to a new version of the track to a new location in the second cache 18.

After writing the new track from blocks 292, 298 or 300, the cache manager 24 invalidates (at block 302) the stale version of the track in the second cache 18 and updates (at block 304) the second cache control block 120 (FIG. 5) for the track indicating the new location in the second cache 18 and updates the sector map 129 indicating the sectors in the second cache 18 now having data for the track, i.e., non-empty sectors. The cache manager 24 further moves (at block 306) the entry for the track in the LRU list 74 to the MRU end of the LRU list 74.

FIG. 12 illustrates an embodiment of operations performed by the cache manager 24 to add tracks from the first stride from the first cache 14 to the second stride in the second cache 18. The cache manager 24 creates (at block 322) stride information 130 (FIG. 6) for the second stride indicating the tracks 134 from the first stride being added and indicating the occupancy 136 as full. For each track in the first stride being added, the cache manager 24 performs (at block 324) the operations in FIG. 11 to add a track to the LSA in the second cache 24 for the track being demoted from the first cache 14, which may involve combining the sectors of a partial track being demoted with the sectors of a stale version of the track in the second cache 18 which are not included in the partial track being demoted from the first cache 14.

FIG. 13 illustrates an embodiment of operations performed by the cache manager 24 to free space in the second cache 18 for new tracks to add to the second cache 18, i.e., tracks being demoted from the first cache 14. Upon initiating this operation (at block 350) the cache manager 24 determines (at block 352) unmodified tracks in the second cache 18 from the LRU end of the unmodified LRU list 74 and invalidates (at block 354) the determined unmodified tracks without destaging the invalidated unmodified tracks to the storage 10, and also removes the invalidated unmodified tracks from the unmodified LRU list 74 and indicates the track as invalid 128 in the second cache control block 120 for the track. Further, the tracks selected by the cache manager 24 for demotion from the second cache 18 may be from different strides formed in the second cache 18. Further, strides in the second cache may include both valid and invalid tracks, where tracks are invalidated by demoting from the second cache 18 or by the track being updated in the first cache 18.

In certain embodiments, the cache manager 24 uses different track demotion algorithms to determine tracks to demote from the first cache 14 and the second cache 18 by using separate LRU lists 58 and 74 for the first 14 and second 18 caches 18, respectively, to determine the tracks to demote. The algorithms used to select tracks for demotion in the first 14 and second 18 caches may consider characteristics of the tracks in the first 14 and second 18 caches to determine tracks to demote first.

FIG. 14 illustrates an embodiment of operations performed by the cache manager 24 to retrieve requested tracks for a read request from the caches 14 and 18 and storage 10. The storage manager 22 processing the read request may submit requests to the cache manager 24 for the requested tracks. Upon receiving (at block 450) the request for the tracks, the cache manager 24 uses (at block 454) the first cache track index 50 to determine whether all of the requested tracks are in the first cache 14. If (at block 454) all requested tracks are not in the first cache 14, then the cache manager 24 uses (at block 456) the second cache track index 70 to determine any of the requested tracks in the second cache 18 not in the first cache 14. If (at block 458) there are any requested tracks not found in the first 14 and second 18 caches, then the cache manager 24 determines (at block 460) any of the requested tracks in the storage 10, from the second cache track index 70, not in the first 14 and the second 18 caches. The cache manager 24 then promotes (at block 462) any of the determined tracks in the second cache 18 and the storage 10 to the first cache 14. The cache manager 24 uses (at block 464) the first cache track index 50 to retrieve the requested tracks from the first cache 14 to return to the read request. The entries for the retrieved tracks are moved (at block 466) to the MRU end of the LRU list 54, 56, 58 including entries for the retrieved tracks. With the operations of FIG. 13, the cache manager 24 retrieves requested tracks from a highest level cache 14, then second cache 18 first before going to the storage 10, because the caches 14 and 18 would have the most recent modified version of a requested track. The most recent version is first found in the first cache 14, then the second cache 18 if not in the first cache 14 and then the storage 10 if not in either cache 14, 18.

With the operations of FIG. 14, the cache manager 24 retrieves requested tracks from a highest level cache 14, then second cache 18 first before going to the storage 10, because the caches 14 and 18 would have the most recent modified version of a requested track. The most recent version is first found in the first cache 14, then the second cache 18 if not in the first cache 14 and then the storage 10 if not in either cache 14, 18.

Described embodiments provide techniques to group tracks in a first cache in strides defined according to a RAID configuration for the second cache, so that tracks in the first cache can be grouped in strides to a second cache. The tracks cached in the second cache may then be grouped into strides, defined according to a RAID configuration for the storage, and then written to the storage system.

Described embodiments provide techniques to demote tracks from a first cache to a second cache having partial tracks, so the sectors in the partial track being demoted are combined with any sectors not included in the partial track being demoted in an older version of the track in the second cache. The combined track may then be written to a new location in the second cache.

The described operations may be implemented as a method, apparatus or computer program product using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. Accordingly, aspects of the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the embodiments may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Aspects of the present invention are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the present invention(s)” unless expressly specified otherwise.

The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.

The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.

Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the present invention.

Further, although process steps, method steps, algorithms or the like may be described in a sequential order, such processes, methods and algorithms may be configured to work in alternate orders. In other words, any sequence or order of steps that may be described does not necessarily indicate a requirement that the steps be performed in that order. The steps of processes described herein may be performed in any order practical. Further, some steps may be performed simultaneously.

When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the present invention need not include the device itself.

The illustrated operations of the figures show certain events occurring in a certain order. In alternative embodiments, certain operations may be performed in a different order, modified or removed. Moreover, steps may be added to the above described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.

The foregoing description of various embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims herein after appended. 

What is claimed is:
 1. A method for managing data in a cache system comprising a first cache, a second cache, and a storage system, comprising: determining a track to demote from the first cache to the second cache comprising a partial track that includes data for less than all sectors of the track, wherein the track in the first cache corresponds to a track in the storage system and is comprised of a plurality of sectors; determining whether the second cache includes a stale version of the track being demoted from the first cache; in response to determining that the second cache includes the stale version of the track, determining whether the stale version of the track includes data for track sectors of the track being demoted from the first cache that do not include data; combining the data for the sectors from the track demoted from the first cache with the data for the track sectors from the stale version that includes data for the track sectors in the track being demoted from the first cache that do not include data into a first new version of the track; writing the first new version of the track to the second cache; and writing the track being demoted from the first cache to a second new version of the track in the second cache in response to determining that the second cache does not include the stale version, wherein the second new version of the track has data of the partial track in non-empty sectors and includes empty sectors to include data for less than all the sectors of the track.
 2. The method of claim 1, wherein the operations further comprise: invalidating the stale version of the track in the second cache in response to writing the first or second new version of the track to the second cache.
 3. The method of claim 1, wherein the first new version of the track comprises a partial track including data for less than all the sectors of the track in response to the stale version of the track not including data for the sectors of the track being demoted that do not include data.
 4. The method of claim 1, wherein the first new version of the track comprises a full track including data for all the sectors of the track in response to the stale version of the track including data for the sectors of the track being demoted that do not include data.
 5. The method of claim 1, wherein the operations further comprise: writing the track being demoted to a third new version of the track in response to determining that the track being demoted includes data for all the sectors of the track.
 6. The method of claim 1, wherein the stale version of the track includes data for sectors of the track previously demoted from the first cache to the second cache and wherein the first new version of the track is written to a location in the second cache not including the stale version of the track.
 7. The method of claim 1, wherein the demoted track from the first cache is included in a first stride having tracks to demote from the first track, wherein the operations further comprise: writing the tracks from the first stride to a second stride in the second cache that has no valid tracks.
 8. The method of claim 7, wherein the operations of determining the track to demote, determining whether the second cache includes the stale version, determining whether the stale version includes data for sectors not included in the track being demoted, combining the data for the sectors, and writing the first or second new version are performed for each track in the first stride written to the second stride.
 9. The method of claim 8, wherein forming the first stride of tracks comprising forming a stride for a Redundant Array of Independent Disk (RAID) configuration based on a RAID configuration defined for the second cache as having a plurality of solid state storage devices, wherein the first stride of tracks from the first cache are striped across the solid state storage devices to form the second stride in the second cache.
 10. The method of claim 1, wherein the first cache is a faster access device than the second cache and wherein the second cache is a faster access device than the storage devices. 